Method and apparatus for media scene description

ABSTRACT

Systems, methods, and devices for managing media storage and delivery, including obtaining, by a media access function (MAF), a glTF file corresponding to a scene; determining that the glTF file has a CBOR format; converting the glTF file into a converted glTF file having a JSON format using a first CBOR parser function implemented by the MAF; and obtaining media content corresponding to the scene based on the converted glTF file.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from U.S. Provisional Application No.63/137,274, filed on Jan. 14, 2021, the disclosures of which isincorporated herein by reference in its entirety.

FIELD

Embodiments of the present disclosure relate to system design to supportmedia objects using a 3D modeling syntax, implement media syntax tosupport various media codecs, containers, and formats, manage mediastorage and delivery method through predefined programming interfaces,and provide media buffer control and rendering functions.

BACKGROUND

The Graphics Language Transmission Format (glTF) is an API-neutralruntime asset 3D modeling delivery format. Compared with traditional 3Dmodeling tools, glTF provides a more efficient, extensible,interoperable format for the transmission and loading of 3D content.glTF2.0 is the most recent version of the glTF specification written bythe Khronos 3D Group. This format supports a simple scene graph formatthat is generally capable of supporting static (untimed) objects inscenes, including “png” and “jpeg” image formats. glTF2.0 supportssimple animations, including support for translate, rotate, and scale,of basic shapes described using the glTF primitives, i.e. for geometricobjects. glTF2.0 does not support timed media, and hence does notsupport video nor audio.

“Information technology—Coding of audiovisual objects—Part 12: ISO basemedia file format”, ISO/IEC 14496-12 (December 2015), “Draft of FDIS ofISO/IEC 23000-19 Common Media Application Format for Segmented Media”,ISO/IEC JTC1/SC29/WG11 MPEG117/16819 (April 2017); and “Text of ISO/IECFDIS 23009-1 4th edition”, ISO/IEC JTC 1/SC 29/WG 11 N18609 (August2019), and the glTF2.0 specification are incorporated herein byreference in their entirety.

SUMMARY

According to an embodiment, a method of managing media storage anddelivery is implemented by at least one processor and includes:obtaining, by a media access function (MAF), a glTF file correspondingto a scene; determining that the glTF file has a CBOR format; convertingthe glTF file into a converted glTF file having a JSON format using afirst CBOR parser function implemented by the MAF; and obtaining mediacontent corresponding to the scene based on the converted glTF file.

According to an embodiment, a device for managing media storage anddelivery includes at least one memory configured to store program code;and at least one processor configured to read the program code andoperate as instructed by the program code, the program code including:first obtaining code configured to cause the at least one processor toobtain, by a media access function (MAF), a glTF file corresponding to ascene; first determining code configured to cause the at least oneprocessor to determine that the glTF file has a CBOR format; firstconverting code configured to cause the at least one processor toconvert the glTF file into a converted glTF file having a JSON formatusing a first CBOR parser function implemented by the MAF; and secondobtaining code configured to cause the at least one processor to obtainmedia content corresponding to the scene based on the converted glTFfile.

According to an embodiment, a non-transitory computer-readable mediumstoring instructions, the instructions including: one or moreinstructions that, when executed by at least one processor of a devicefor managing media storage and delivery, are configured to cause the atleast one processor to: obtain, by a media access function (MAF), a glTFfile corresponding to a scene; determine that the glTF file has a CBORformat; convert the glTF file into a converted glTF file having a JSONformat using a first CBOR parser function implemented by the MAF; andobtain media content corresponding to the scene based on the convertedglTF file.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosedsubject matter will be more apparent from the following detaileddescription and the accompanying drawings in which:

FIG. 1 is a diagram of an environment in which methods, apparatuses andsystems described herein may be implemented, according to embodiments.

FIG. 2 is a block diagram of example components of one or more devicesof FIG. 1, according to embodiments.

FIG. 3 is a schematic illustration of glTF scene description objects,according to embodiments.

FIG. 4 is a schematic illustration of the media scene description systemreference architecture, according to embodiments.

FIG. 5 is an example of glTF JavaScript Object Notation (JSON) formatrepresentation, according to embodiments.

FIG. 6 is an example of MPEG glTF extension, according to embodiments.

FIG. 7A is an illustration of a file having a JSON format, according toembodiments.

FIG. 7B is an illustration of a file having a CBOR format, according toembodiments.

FIG. 8 is an illustration of an example of glTF syntax, according toembodiments.

FIGS. 9A-9C are diagrams of example processes for managing media storageand delivery according to embodiments.

DETAILED DESCRIPTION

FIG. 1 is a diagram of an environment 100 in which methods, apparatuses,and systems described herein may be implemented, according toembodiments. As shown in FIG. 1, the environment 100 may include a userdevice 110, a platform 120, and a network 130. Devices of theenvironment 100 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

The user device 110 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith platform 120. For example, the user device 110 may include acomputing device (e.g., a desktop computer, a laptop computer, a tabletcomputer, a handheld computer, a smart speaker, a server, etc.), amobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearabledevice (e.g., a pair of smart glasses or a smart watch), or a similardevice. In some implementations, the user device 110 may receiveinformation from and/or transmit information to the platform 120.

The platform 120 includes one or more devices as described elsewhereherein. In some implementations, the platform 120 may include a cloudserver or a group of cloud servers. In some implementations, theplatform 120 may be designed to be modular such that software componentsmay be swapped in or out depending on a particular need. As such, theplatform 120 may be easily and/or quickly reconfigured for differentuses.

In some implementations, as shown, the platform 120 may be hosted in acloud computing environment 122. Notably, while implementationsdescribed herein describe the platform 120 as being hosted in the cloudcomputing environment 122, in some implementations, the platform 120 maynot be cloud-based (i.e., may be implemented outside of a cloudcomputing environment) or may be partially cloud-based.

The cloud computing environment 122 includes an environment that hoststhe platform 120. The cloud computing environment 122 may providecomputation, software, data access, storage, etc. services that do notrequire end-user (e.g., the user device 110) knowledge of a physicallocation and configuration of system(s) and/or device(s) that hosts theplatform 120. As shown, the cloud computing environment 122 may includea group of computing resources 124 (referred to collectively as“computing resources 124” and individually as “computing resource 124”).

The computing resource 124 includes one or more personal computers,workstation computers, server devices, or other types of computationand/or communication devices. In some implementations, the computingresource 124 may host the platform 120. The cloud resources may includecompute instances executing in the computing resource 124, storagedevices provided in the computing resource 124, data transfer devicesprovided by the computing resource 124, etc. In some implementations,the computing resource 124 may communicate with other computingresources 124 via wired connections, wireless connections, or acombination of wired and wireless connections.

As further shown in FIG. 1, the computing resource 124 includes a groupof cloud resources, such as one or more applications (“APPs”) 124-1, oneor more virtual machines (“VMs”) 124-2, virtualized storage (“VSs”)124-3, one or more hypervisors (“HYPs”) 124-4, or the like.

The application 124-1 includes one or more software applications thatmay be provided to or accessed by the user device 110 and/or theplatform 120. The application 124-1 may eliminate a need to install andexecute the software applications on the user device 110. For example,the application 124-1 may include software associated with the platform120 and/or any other software capable of being provided via the cloudcomputing environment 122. In some implementations, one application124-1 may send/receive information to/from one or more otherapplications 124-1, via the virtual machine 124-2.

The virtual machine 124-2 includes a software implementation of amachine (e.g., a computer) that executes programs like a physicalmachine. The virtual machine 124-2 may be either a system virtualmachine or a process virtual machine, depending upon use and degree ofcorrespondence to any real machine by the virtual machine 124-2. Asystem virtual machine may provide a complete system platform thatsupports execution of a complete operating system (“OS”). A processvirtual machine may execute a single program, and may support a singleprocess. In some implementations, the virtual machine 124-2 may executeon behalf of a user (e.g., the user device 110), and may manageinfrastructure of the cloud computing environment 122, such as datamanagement, synchronization, or long-duration data transfers.

The virtualized storage 124-3 includes one or more storage systemsand/or one or more devices that use virtualization techniques within thestorage systems or devices of the computing resource 124. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

The hypervisor 124-4 may provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as the computing resource124. The hypervisor 124-4 may present a virtual operating platform tothe guest operating systems, and may manage the execution of the guestoperating systems. Multiple instances of a variety of operating systemsmay share virtualized hardware resources.

The network 130 includes one or more wired and/or wireless networks. Forexample, the network 130 may include a cellular network (e.g., a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the Public Switched Telephone Network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 1 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may beimplemented within a single device, or a single device shown in FIG. 1may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) of theenvironment 100 may perform one or more functions described as beingperformed by another set of devices of the environment 100.

FIG. 2 is a block diagram of example components of one or more devicesof FIG. 1. The device 200 may correspond to the user device 110 and/orthe platform 120. As shown in FIG. 2, device 200 may include a bus 210,a processor 220, a memory 230, a storage component 240, an inputcomponent 250, an output component 260, and a communication interface270.

The bus 210 includes a component that permits communication among thecomponents of the device 200. The processor 220 is implemented inhardware, firmware, or a combination of hardware and software. Theprocessor 220 is a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, theprocessor 220 includes one or more processors capable of beingprogrammed to perform a function. The memory 230 includes a randomaccess memory (RAM), a read only memory (ROM), and/or another type ofdynamic or static storage device (e.g., a flash memory, a magneticmemory, and/or an optical memory) that stores information and/orinstructions for use by the processor 220.

The storage component 240 stores information and/or software related tothe operation and use of the device 200. For example, the storagecomponent 240 may include a hard disk (e.g., a magnetic disk, an opticaldisk, a magneto-optic disk, and/or a solid state disk), a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of non-transitory computer-readablemedium, along with a corresponding drive.

The input component 250 includes a component that permits the device 200to receive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, the input component 250 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). The output component 260 includes a component that providesoutput information from the device 200 (e.g., a display, a speaker,and/or one or more light-emitting diodes (LEDs)).

The communication interface 270 includes a transceiver-like component(e.g., a transceiver and/or a separate receiver and transmitter) thatenables the device 200 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. The communication interface 270 may permit thedevice 200 to receive information from another device and/or provideinformation to another device. For example, the communication interface270 may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a Wi-Fi interface, a cellularnetwork interface, or the like.

The device 200 may perform one or more processes described herein. Thedevice 200 may perform these processes in response to the processor 220executing software instructions stored by a non-transitorycomputer-readable medium, such as the memory 230 and/or the storagecomponent 240. A computer-readable medium is defined herein as anon-transitory memory device. A memory device includes memory spacewithin a single physical storage device or memory space spread acrossmultiple physical storage devices.

Software instructions may be read into the memory 230 and/or the storagecomponent 240 from another computer-readable medium or from anotherdevice via the communication interface 270. When executed, softwareinstructions stored in the memory 230 and/or the storage component 240may cause the processor 220 to perform one or more processes describedherein. Additionally, or alternatively, hardwired circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

The number and arrangement of components shown in FIG. 2 are provided asan example. In practice, the device 200 may include additionalcomponents, fewer components, different components, or differentlyarranged components than those shown in FIG. 2. Additionally, oralternatively, a set of components (e.g. one or more components) of thedevice 200 may perform one or more functions described as beingperformed by another set of components of the device 200.

Referring to FIG. 3, the Graphics Language Transmission Format (glTF) isan application programming interface (API)-neutral runtime asset 3Dmodeling delivery format. Compared with traditional 3D modeling tools,glTF provides a more efficient, extensible, interoperable format for thetransmission and loading of 3D content.

A glTF scene may be a combination of multiple glTF assets. The glTFassets may be JavaScript Object Notation (JSON)-formatted filescontaining a full scene description which may include, for example, ascene object 301, node 302, camera 303, mesh 304, light 305, animation306, accessor 307, material 308, skin 309, bufferview 310, technique311, texture 312, buffer 313, program 314, image 315, sampler 316,shader 317, plus supporting external data.

glTF also supports external data sources which may be referenced in anyabove-mentioned scene objects. In embodiments, a binary file may be usedfor animation 306 or other buffer-based data 313. An image file may beused for object textures 312.

Referring to FIG. 5, as mentioned above, a glTF scene may be organizedin JSON format. A glTF asset may include zero or more scenes 503, whichmay be the set of visual objects to render. Scenes may be defined in ascene array. In example illustrated in FIG. 5, there is a single scene506 with a single node 501, although embodiments are not limitedthereto. Various parameters that may be associated with each nodeobject. For example, name 502 may specify the name of the node object,and scene name 504 may specify the name of the single scene.

The glTF scene assets may be consumed by a presentation engine forrendering a 3D or immersive scene to users. The existing glTF syntaxonly supports 3D objects including static or computer-generatedanimations. There is no support for media types such as video or audio,let alone rendering those video/audio media types.

Meanwhile, existing glTF can not describe a scene using geographicalcoordinate systems, which in some media presentation scenarios, such afeature is desired.

Therefore, there is a need to extend the glTF to support media typesincludes traditional 2D flat video, immersive media content such asvirtual reality (VR), augmented reality (AR), extended reality (XR), andspatial audios. This may require an extension to support video/audiosyntax and a system for media deliveries and render

Moving Picture Experts Group (MPEG) defines some extensions on top ofthe glTF specification to support immersive media content. Referring toFIG. 3, new extensions are MPEG_media 330, MPEG_scene dynamic 331,MPEG_texture_video 333, MEPG_animation_timing 332, MPEG_audio spatial334, MPEG_accessor_timed 335, MPEG_buffer_circular 336. In FIG. 3generally, elements with rounded outlines, for example elements 301-317,may be glTF elements, and elements with square outlines, for exampleelements 330-336, may correspond to MPEG-based extensions of the glTFspecification, although embodiments are not limited thereto.

If MPEG_media 330 as a root identifier, if specified, then MPEG_mediamay be supported. Referring to FIG. 6, the syntax to support MPEG mediamay be declared as the top-level JSON syntax. Syntax from 601 to 604 inFIG. 6 may be presented exactly as shown if supported.

Scene Updates may be expressed using the JSON Patch protocol andMPEG_scene_dynamic 331 may be used to support JSON patch protocol.

MPEG texture video extension, identified by MPEG_texture_video 333, mayprovide the possibility to link a glTF texture object to MPEG media andits respective track, listed by an MPEG_media object. MPEG texture videoextension may also provide a reference to the MPEG_accessor_timed 335,where the decoded timed texture will be made available.

The MPEG_audio spatial 334 extension may support multiple audio types.

In order to support timed data access, the buffer element may beextended to provide circular buffer functionality. The extension isnamed MPEG_buffer_circular 336 and may be included as part of the glTF“buffers” objects, for example buffer 313.

Above MEPG extensions may allow for the creation of immersiveexperiences using glTF. Eventually the glTF assets with MPEG extensionmay be used to be load into a rendering engine for visualization.

Referring to FIG. 4, a reference media scene description architecture400 illustrates an example of how MPEG extensions may be used to supportmedia type such as audio/video. The media contents may be retrievedusing a Media Retrieval Engine and Media Access Functions (MAF) 402 fromexternal sources such as a media cloud 401, processed using videodecoder 403, audio decoder 404, and other data compressor 405, bufferedin video buffer 406, audio buffer 407, and other buffer 408, andrendered by a presentation engine 409. In some cases, media content maybe stored in local storage 410.

Referring to FIG. 4, the MPEG scene description extensions may decouplethe Presentation Engine 409 from the Media Retrieval Engine 402.Presentation Engine 409 and Media Retrieval Engine 402 may communicatethrough the predefined programming interfaces, which allows thePresentation Engine 409 to request media data required for the renderingof the scene. The Media Retrieval Engine 402 may retrieve the requestedmedia and make it available in a timely manner and in a format that canbe immediately processed by the Presentation Engine 409. For instance, arequested media asset may be compressed and residing in the network, sothe Media Retrieval Engine 402 will retrieve and decode the asset andpass the resulting media data to the Presentation Engine 409 forrendering. The media data may be passed in form of buffers from theMedia Retrieval Engine 402 to the Presentation Engine 409. The requestsfor media data may be passed through a Media Retrieval API from thePresentation Engine 409 to the Media Retrieval Engine 402. For flexibleuse of video decoding resource, the Video Decoder 403 may be used. Whenthe Video Decoder 403 is used, the Presentation Engine 409 may provideinformation for input formatting and output formatting to the VideoDecoder 403 through Application Configuration APIs.

As discussed above, glTF syntax may be expressed in a JSON file. TheInternet Engineering Task Force (IETF) Concise Binary ObjectRepresentation (CBOR) may represent a concise data format compared withthe traditional JSON format. CBOR relates to similar data objects likeJSON in a name/value pair format, but expressed in a binary and compactway, also with much more support with key-value types. A size of a filein CBOR format may be smaller than a corresponding file in JSON format.In some cases, the CBOR file may be more than 50% smaller than thecorresponding JSON file. CBOR is registered in Internet Assigned NumbersAuthority (IANA) as “application/cbor”.

CBOR may be used as one of the glTF interchangeable compressed fileformats which also has been widely supported due to its compact datasize and interchangeability with JSON.

Information in CBOR is stored in binary form. Because many use cases forinformation includes machines to understand the data, a binary dataformat may have speed advantages over human-readable data formats likeJSON or XML which may need to be parsed each time the computer ormachine is used to understand the data stored.

FIG. 7A illustrates an example of a file in JSON format, and FIG. 7Billustrates an example of a corresponding file in CBOR format. Forexample, the character “a” (711) in the JSON formatted file of FIG. 7Amay correspond to 0x61 (721) in the CBOR formatted file of FIG. 7B.Similarly, the character “b” (712) in the JSON formatted file of FIG. 7Amay correspond to 0x62 (722) in the CBOR formatted file of FIG. 7B, andthe character “c” (713) in the JSON formatted file of FIG. 7A maycorrespond to 0x63 (723) in the CBOR formatted file of FIG. 7B.

The usage of CBOR compared with JSON for scene description may bringadvantages in terms of small data size, support of multiple key-valuetypes instead of just String object in JSON. Function programminginterfaces may be used in the presented media scene descriptionreference architecture, more precisely in the media access functionmodule.

Because the support of CBOR by glTF is gaining popularity, such supportmay be added into MPEG scene description in order to, for example,increase glTF file format interoperability, reduce file size for localstorage or cache, and reduce glTF file transfer latency with minimumprocessing power at MAF 402.

A CBOR parser function according to embodiments may be implemented byMAF 402 to translate CBOR input into glTF native supported JSON formatand also could be used as a file compressor to save the large glTF fileinto local storage or cache 410.

The CBOR parser API offers one of the methods such as cbor2Json( ),json2Cbor and save( ), as shown in the Table 1 below:

TABLE 1 Method Brief Description cbor2Json (FILE) Convert a CBOR formatinto a JSON format json2Cbor (FILE) Convert a JSON format into a CBORformat cbor2Json (Object) Convert a CBOR data blob into a JSON format

A detailed interface description may be as follows:

interface InputFileParser {   readonly attribute FILE inputFileName; readonly attribute FILE outputFilename;  readonly attribute CBORcborDataBlob;   FILE cbor2Json( )(FILE cborInput);  FILE json2Cbor(FILEjsonInput);  FILE  cbor2Json(CBOR cborDataBlob);   bool save( ); };};

The above proposed functions may be used for example in variousscenarios as follows.

Referring to FIG. 8, a glTF “url” or “uri” syntax may point to a CBORbinary data blob (802). In embodiments, there may be two ways to specifyif binary is indeed a CBOR data format. According to Example 1, aMultipurpose Internet Mail Extension (MIME) type may be signaled whichspecifies a “mimeTypes” with “application/cbor” (801). According toExample 2, a prefix “application/cbor;” may be included in front ofactual binary data. Examples 1 and 2 may be used together. In any case,a function called “cbor2Json(Object)” which takes a CBOR binary data maybe called to parse the CBOR file format into a JSON.

If an input glTF is in CBOR format, the output may be a glTF by usingcbor2Json( ) API

If an input is in a native glTF format, then no conversion may benecessary.

For local storage or cache purpose, a glTF file may be saved as a CBORby using json2Cbor( ) and save( ) interface.

Accordingly, embodiments may relate to methods of providing glTF fileformat interoperability with CBOR, reducing file size for local storageor cache, increasing, data transfer speed, reducing file transferlatency.

Referring to FIGS. 9A-9C, processes 900A, 900B, and 900C for managingmedia storage and delivery are described below.

FIG. 9A is a flowchart of an example process 900A for managing mediastorage and delivery.

As shown in FIG. 9A, process 900A may include obtaining, by a mediaaccess function (MAF), a glTF file corresponding to a scene (block 911).In embodiments, the MAF may correspond to MAF 402.

As further shown in FIG. 9A, process 900A may include determining thatthe glTF file has a CBOR format (block 912).

As shown in FIG. 9A, process 900A may include converting the glTF fileinto a converted glTF file having a JSON format using a first CBORparser function implemented by the MAF (block 913).

As shown in FIG. 9A, process 900A may include obtaining media contentcorresponding to the scene based on the converted glTF file (block 914).

In embodiments, the converted glTF file having the JSON format may belarger than the glTF file having the CBOR format.

In embodiments, the MAF may be included in a Moving Picture ExpertsGroup (MPEG) scene description architecture. In embodiments, the MPEGscene description architecture may correspond to media scene descriptionarchitecture 400.

In embodiments, the first CBOR parser function may be implemented usingan API associated with the MAF. In embodiments, the API may correspondto any API discussed above.

FIG. 9B is a flowchart of an example process 900B for managing mediastorage and delivery. In embodiments, one or more blocks of process 900Bmay be performed in combination with one or more blocks of process 900A.For example, one or more blocks of process 900B may be performed afterone or more blocks of process 900A.

As shown in FIG. 9B, process 900B may include obtaining from theconverted glTF file a uniform resource locator (URL) parameterindicating a binary data blob (block 921).

As further shown in FIG. 9B, process 90B may include determining thatthe binary data blob has the CBOR format (block 922).

As further shown in FIG. 9B, process 900B may include converting thebinary data blob into an object having the JSON format using a secondCBOR parser function implemented by the MAF (block 923).

In embodiments, the binary data blob may be determined to have the CBORformat based on a Multipurpose Internet Mail Extension (MIME) type thatis signaled in the glTF file.

In embodiments, the binary data blob may be determined to have the CBORformat based on a prefix included at a beginning of the binary datablob.

In embodiments, the binary data blob may be determined to have the CBORformat based on a Multipurpose Internet Mail Extension (MIME) type thatis signaled in the glTF file and a prefix included at a beginning of thebinary data blob.

FIG. 9C is a flowchart of an example process 900C for managing mediastorage and delivery. In embodiments, one or more blocks of process 900Cmay be performed in combination with one or more blocks of processes900A and/or 900B. For example, one or more blocks of process 900C may beperformed after one or more blocks of process 900A, or after one or moreblocks of process 900B.

As shown in FIG. 9C, process 900C may include re-converting theconverted glTF file into a re-converted glTF having the CBOR formatusing a JSON parser function implemented by the MAF (block 931).

As further shown in FIG. 9C, process 900C may include storing there-converted glTF file in at least one of a local storage or a cache(block 932).

In embodiments, the re-converted glTF file having the CBOR format may besmaller than the converted glTF file having the JSON format.

In embodiments, the JSON parser function may be implemented using anapplication programming interface associated with the MAF. Inembodiments, the API may correspond to any API discussed above.

Although FIGS. 9A-9C show example blocks of processes 900A, 900B, and900C, in some implementations, of processes 900A. 900B, and 900C mayinclude additional blocks, fewer blocks, different blocks, ordifferently arranged blocks than those depicted in FIGS. 9A-9C.Additionally, or alternatively, two or more of the blocks of processesof processes 900A, 900B, and 900C may be performed in parallel. Inembodiments, any one or more blocks of processes 900A, 900B, and 900Cmay be combined with any other one or more blocks of processes 900A,900B, and 900C in any order, and any one or more of any blocks ofprocesses 900A, 900B, and 900C may be split or combined as desired.

Further, the proposed methods may be implemented by processing circuitry(e.g., one or more processors or one or more integrated circuits). Inone example, the one or more processors execute a program that is storedin a non-transitory computer-readable medium to perform one or more ofthe proposed methods.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, it should be understoodthat software and hardware may be designed to implement the systemsand/or methods based on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method of managing media storage and delivery,the method being implemented by at least one processor and comprising:obtaining, by a media access function (MAF), a Graphics LanguageTransmission Format (glTF) file corresponding to a scene; determiningthat the glTF file has a Concise Binary Object Representation (CBOR)format; converting the glTF file into a converted glTF file having aJavaScript Object Notation (JSON) format using a first CBOR parserfunction implemented by the MAF; and obtaining media contentcorresponding to the scene based on the converted glTF file.
 2. Themethod of claim 1, wherein the converted glTF file having the JSONformat is larger than the glTF file having the CBOR format.
 3. Themethod of claim 1, wherein the MAF is included in a Moving PictureExperts Group (MPEG) scene description architecture.
 4. The method ofclaim 1, wherein the first CBOR parser function is implemented using anapplication programming interface associated with the MAF.
 5. The methodof claim 1, further comprising: re-converting the converted glTF fileinto a re-converted glTF file having the CBOR format using a JSON parserfunction implemented by the MAF; and storing the re-converted glTF filein at least one of a local storage or a cache.
 6. The method of claim 5,wherein the re-converted glTF file having the CBOR format is smallerthan the converted glTF file having the JSON format.
 7. The method ofclaim 5, wherein the JSON parser function is implemented using anapplication programming interface associated with the MAF.
 8. A devicefor managing media storage and delivery, the device comprising: at leastone memory configured to store program code; and at least one processorconfigured to read the program code and operate as instructed by theprogram code, the program code including: first obtaining codeconfigured to cause the at least one processor to obtain, by a mediaaccess function (MAF), a Graphics Language Transmission Format (glTF)file corresponding to a scene; first determining code configured tocause the at least one processor to determine that the glTF file has aConcise Binary Object Representation (CBOR) format; first convertingcode configured to cause the at least one processor to convert the glTFfile into a converted glTF file having a JavaScript Object Notation(JSON) format using a first CBOR parser function implemented by the MAF;and second obtaining code configured to cause the at least one processorto obtain media content corresponding to the scene based on theconverted glTF file.
 9. The device of claim 8, wherein the convertedglTF file having the JSON format is larger than the glTF file having theCBOR format.
 10. The device of claim 8, wherein the MAF is included in aMoving Picture Experts Group (MPEG) scene description architecture. 11.The device of claim 8, wherein the first CBOR parser function isimplemented using an application programming interface associated withthe MAF.
 12. The device of claim 8, wherein the program code furtherincludes: re-converting code configured to cause the at least oneprocessor to re-convert the converted glTF file into a re-converted glTFfile having the CBOR format using a JSON parser function implemented bythe MAF; and storing code configured to cause the at least one processorto store the re-converted glTF file in at least one of a local storageor a cache.
 13. The device of claim 12, wherein the re-converted glTFfile having the CBOR format is smaller than the converted glTF filehaving the JSON format.
 14. The device of claim 12, wherein the JSONparser function is implemented using an application programminginterface associated with the MAF.
 15. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by at least oneprocessor of a device for managing media storage and delivery, areconfigured to cause the at least one processor to: obtain, by a mediaaccess function (MAF), a Graphics Language Transmission Format (glTF)file corresponding to a scene; determine that the glTF file has aConcise Binary Object Representation (CBOR) format; convert the glTFfile into a converted glTF file having a JavaScript Object Notation(JSON) format using a first CBOR parser function implemented by the MAF;and obtain media content corresponding to the scene based on theconverted glTF file.
 16. The non-transitory computer-readable medium ofclaim 15, wherein the converted glTF file having the JSON format islarger than the glTF file having the CBOR format.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the first CBOR parserfunction is implemented using an application programming interfaceassociated with the MAF.
 18. The non-transitory computer-readable mediumof claim 15, wherein the one or more instructions are further configuredto cause the at least one processor to: re-convert the converted glTFfile into a re-converted glTF file having the CBOR format using a JSONparser function implemented by the MAF; and store the re-converted glTFfile in at least one of a local storage or a cache.
 19. Thenon-transitory computer-readable medium of claim 18, wherein there-converted glTF file having the CBOR format is smaller than theconverted glTF file having the JSON format.
 20. The non-transitorycomputer-readable medium of claim 18, wherein the JSON parser functionis implemented using an application programming interface associatedwith the MAF.